Indicate releases are now considered stable. Indicate SemVer is used as inferred from prior text.

Description

Please include a summary of the change and include relevant motivation and context.

...

Checklist:

• The make buildall command has been run successfully without any error or warning.
• Any new code line is covered by unit tests and the coverage has not dropped.
• Any new code follows the style guidelines of this project.
• The code changes have been self-reviewed.
• Corresponding changes to the documentation have been made.
• The version has been updated in the VERSION file.

Type of change:

• Minor non-breaking change (e.g., bug fix, dependencies updates) → The patch number in the VERSION file has been increased.
• New feature (non-breaking change which adds functionality) → The minor number in the VERSION file has been increased.
• Breaking change (fix or feature that would cause existing functionality to not work as expected) → The major number in the VERSION file has been increased.
• Automation.
• Documentation.
• Example.
• Testing.